This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
PYPE-778: [Maya][Redshift] - RenderPass token breaks render publishing #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antirotor
changed the title
Tilix4
referenced
this pull request
in Tilix4/OpenPype
Jan 20, 2023
Fix: Published workfile relative paths are not correctly remapped
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using
RenderPasstoken with Redshift in image prefix is breaking render publishing.Redshift is appending AOV name to image prefix automatically if AOVs are enabled. Explicitly stating image prefix will double it in resulting name:
will result in
It will also not work when multipart EXRs are enabled and in that context it doesn't even make sense.
This PR is modifying render settings validator to trigger when
<RenderPass>token is found in image prefix for Redshift.